OpenEdge Application Server:<br />Administration Defining a Web application for the WSA

If you are running a production server, or if you do not want to lose your deployed Web services when installing another version of OpenEdge, copy the entire sample WSA Web application directory tree to another disk location, outside the OpenEdge installation directory. For an example of how this might be done see the information on copying the WSA sample Web application in Chapter 4, " Configuring a Web Services Adapter Installation."

Configure the JSE to recognize the WSA Web application. Depending upon the JSE, you might have to edit one of its configuration files or install the WSA Web application by using a browser-based administration interface. In addition, each JSE typically has a directory where a Web application resides. See your JSE vendor’s documentation for the specific directory name and a discussion of Web applications.

Note: If a Web application installation procedure requests the path to the Web application deployment file, enter the path to the WSA Web application. For example, the Web application deployment path created during OpenEdge installation is OpenEdge-Install-Directory/servlets/wsa.

If you chose to enable security when you installed the WSA Web application sample, you must now define the WSA administration user names and roles in the JSE. For more information, see your JSE vendor’s documentation. The WSA comes preconfigured to use the role definitions PSCAdmin and PSCOper (case-sensitive). With security enabled, the WSA requires the JSE to authenticate and authorize a user before passing the HTTP request to the JSE for handling. For more information on WSA security, see Chapter 7, " Web Services Adapter Security Configurations."